Rhapsody Developer Release Copyright 1998 by Apple Computer, Inc. All Rights Reserved.
This file contains release notes for the NetworkManager application. NetworkManager lets you edit information in NetInfo domains at a more general level than NetInfoManager allows. Instead of operating on the raw data in NetInfo, as NetInfoManager does, NetworkManager represents this data as hosts, users, groups, and so on.
The following features have been added to NetworkManager but are not currently documented.
When NetworkManager is launched, a user default sets the initial selection of the domain browser. This default, DefaultStartupDomain, can have the following values:
You can set this default in a Terminal shell by entering the following at the command line:
defaults write NetworkManager DefaultStartupDomain RootDomain
NetworkManager remember the last selected domain and uses that as the selection for new windows. In the future these defaults will be selectable in a preferences panel.
These new bugs have been identified in the Developer Release.
|
Reference |
2206725 |
|
Problem |
Moving the splitview divider to extremes distorts the contents of the main window. |
|
Description |
Moving the splitview divider either all the way to the top or all the way to the bottom of the window can cause the layout of the window to become incorrect because there are no constraints on the splitview sizing. |
|
Workaround |
Avoid moving the divider to either extreme. If the contents of the window does become distorted, opening a new window is the only way to get a clean window again. Also, the size of the window affects how far you can move the divider so resizing the window to a larger vertical size will give you more room. |
|
Reference |
2209787 |
|
Problem |
Clicking on the Add User button in the Group Detail panel sometimes fails. |
|
Description |
Sometimes if you click the Add User button in the Group Detail panel nothing happens. |
|
Workaround |
Clicking on the Add User button a second time usually brings the panel up properly. |
|
Reference |
2209800 |
|
Problem |
Selecting a non-responsive domain leaves the domain browser selection wrong |
|
Description |
If you click on a domain name in the domain browser that does not respond, NetworkManager displays an error dialog saying that it could not contact the domain. Unfortunately, the path in the domain browser is not reset to the previously selected domain. This leaves the selected domain incompatible with the contents in the tab view in the lower portion of the window. |
|
Workaround |
Selecting a responsive domain resynchronizes the window. |
|
Reference |
2209806 |
|
Problem |
The domain browser should exlude local domains with certain selections. |
|
Description |
Certain types of views, such as the Auto Host Config tab, should have nothing to do with the local domain of a machine, so the domain browser should limit the selection to parent nodes instead of letting you select a local domain. |
|
Workaround |
Take care to select the appropriate domain when working with displays that should exclude local domains. |
|
Reference |
2171222 |
|
Problem |
Editing the user password field doesn't mark the window as needing to be saved |
|
Description |
In the User Details window, changing the value of the password field doesn't properly mark the window as needing to be saved until you exit the password field. |
|
Workaround |
When you have finished typing the new password value, press Tab or click a different text field to mark the window as needing to be saved. |
|
Reference |
2217826 |
|
Problem |
Failure to contact domain if application is launched from command line. |
|
Description |
If NetworkManager.app or NetInfoManager.app is launched from the command line, the application may have difficulty communicating with NetInfo and display an alert panel saying "The domain you have selected, /some/domain is not responding". |
|
Workaround |
Launch NetworkManager.app or NetInfoManager.app from the Workspace instead of from the command line. If you need to launch either application as root for some reason, use AppOpener's Open As Root service menu item. |
|
Reference |
2223952 |
|
Problem |
NetworkManager should handle authenticating non-root users better |
|
Description |
When NetworkManager tries to write information into NetInfo, it prompts for authentication. There are several ways to authenticate for writing in NetInfo. The first method supplies the root password for the machine that is hosting the domain you are writing to. The second is if there is a "_writers" property in the directory being written; the property specifies a list of user names as values, so you can supply the username and password for one of the listed names. The third is similar to the second but offers a finer level of control. If there is a property in the directory being written to which has the format "_writers_propertyname" with a list of user names as values, you can supply the username and password for one of the listed names. For example, if the property "_writers_passwd" appears in a user's entry with a value of their username, the user can change their own password. NetworkManager allows you to authenticate as root or as an individual username by changing the username field of the authentication panel. There are two problems with this: (1) Only root authentications are tracked properly. That is, once you authenticate as root in a domain, you won't be asked to authenticate again. The same is not true for non-root authentication. Each time you write into NetInfo, if you haven't authenticated as root, you are prompted to authenticate. (2) If you supply a username and password other than root in the authentication panel but the username you supply is not listed in either a "_writers" or "_writers_propertyname" property, the write silently fails. |
|
Workaround |
There is no workaround for problem 1; you must continually enter the username and password for non-root authentication. For problem 2, you can verify that information has been written by simply closing the window (or select a different tab for Time Servers and Auto Host Config) and then reopening the window to verify that your changes have been made. |
|
Reference |
2223955 |
|
Problem |
Removing the last item in aliases and netgroups lists doesn't refresh the window. |
|
Description |
When editing a host with NetworkManager, if you try to remove the last item in either the aliases or netgroups lists, the UI isn't properly refreshed. The entries are removed from NetInfo, however. |
|
Workaround |
Close the window and reopen it to refresh the lists. |